The diagram above illustrates the control mechanism utilizedto assocaite bowlers with their teams.
On the left, is shown the TEAMS.HDR file. Assume that thefile has been initialized for eight teams, four bowlers per team. Each team has a header record which includes the Bowler ID's ofits members. These ID's are direct pointers to the appropriaterecord in the BOWLERS.HDR file. Thus, team one has bowlers 1through 4, team two has bowlers 5 through 8, and so on up to teameight, which points to bowlers 29 through 32. This is the way the file would appear after initialilization and before any changes were made.
The BOWLERS.HDR file is shown on the right. There is oneheader record for each bowler which contains, among other data, apointer to the team with which the bowler is associated. Noticethat bowler numbers 33 and higher have 00 in the Team Number field.This indicates that they are substitutes and not members of anyteam. To replace a member who leaves, it is only necessary toupdate the appropriate pointers in these files..eject
.space1
PROGRAMS INCLUDED IN THE SYSTEM
Program Description
------- ----------------------------------
A - Creation/Maintenance Programs
CREATE Initialize League Master Files
SCHEDULE Create Master Schedule File
CHANGE Master File Maintenance Program
B - Weekly Processing Programs
SCORES Enter Scores
RECAP Print Weekly Standings Sheet
C - Reporting Programs
RECORDD Display Team and Bowler Records
RECORDP Print Team and Bowler Records
SORTFILE Print ABC/WIBC Book Average Report (Name sequence)
FINAL Print Final Standings and Averages
D - Special Utility Programs
PRINT Print Utility - Team/Bowler Headers
DETAIL Print Utility - Team/Bowler Detail Records
.eject
.space1
PROGRAM DESCRIPTIONS
A. File Creation/Maintenance Programs
1. CREATE - This program is used to initialize the masterfiles at the begining of the season. The program first promptsfor LEAGUE variable data (League name, number of teams, bowlersper team, handicap basis, and number of weeks in season). Thisinformation is recorded on record #1 of the TEAMS.HDR file.
Next, the system will prompt for team and individual bowlerdata, under control of the variables entered above. It issuggested that the team name begin with the team number for easeof identification on the various reports (e.g. "#1 - The AlleyCats"). Bowler names should be entered as First-name Last-name(e.g. Frank Brown). The SORTFILE program will automaticallyreverse the names prior to sorting to achieve correct sequence. Vacancies should be entered as "*VACANCY" in all caps. If thebowler did not have an average last year, zero ("0") should beentered. This will be the basis for computing improvement on thefinal standings report. The bowlers 21 game average will beautomatically inserted if zero is entered here.
When all regular bowlers have been entered, the system willprompt for substitute names and previous averages. A mask isprovided to facilitate entry of telephone number in the right-most portion of the name field. When all bowler records have beenentered, "*END" should be keyed into the leftmost positions of the name field to complete processing.
2. SCHEDULE - This program permits entry of the leagueschedule. After initializing lane numbers, it prompts for datesand schedules. Month and day are entered as numeric variables,separated by a comma. The team pairings are entered as charactertext. Appropriate spaces should be entered to align the data with the Lane Numbers HEADING line. This approach also permits freeform text to be entered.
NOTE: With the current forms design, a maximum of 18 teamscan be accommodated on an 80 character print line.
3. CHANGE - The master maintenence program permits changes to most of the data in the header records, as well as allowing newbowler records to be added to the files. All bowlers added to the file after initial creation should be added as substitutes. Whenthat person is placed on a team, the pointers controlling teamassignment should be changed using function number 2 - that is,the team header record should be changed to point to the newbolwer number, and the bowler's header record should be changed so that team number is "0". See the File Descriptions section for further information. Where a new bowler is filling a previous"*VACANCY" position, the data can be entered directly into theexisting dummy record.
.EJECT
B. Weekly Processing Programs
1. SCORES - This program posts the weekly bowling results tothe master files. A prompt for month and day of bowling is issued at the start of processing. These constants should be entered asnumeric values, separated by a comma (e.g. 11,24). This date isused on the detail record files.
After date has been entered properly, the program willpresent each team and its bowlers in sequence for posting ofscores. Any game not bowled must be entered as zero; the program will then request entry of blind scores. Four scores must beentered on each line. The example below shows how the scoreswould be entered for a bowler who missed the first 2 games. Theblind score is entered manually and can therefore be a constantscore which is league determined, average, average less 10 pins,or any other appropriate score.
e.g. GAM1 GAM2 GAM3 SER
---- ---- ---- ---
0 0 175 175 Bowler's actual score 164 164 0 328 Avg less 10 pins
In the example above, the scratch score posted to thebowler's record is a 175 series (1 game), while the team score isposted as a 503 series.
Substitutes are indicated by entering 999 as the first gamescore. The system will mark the regular bowlers record as absentand retrieve and display the sub name for verrification. Subs are identified by their bowler ID. If you mis-key and get the wrongsub record, simply enter 999 in the first game again to restart.
In posting scores, you will actually be interactivelybuilding a copy of the score sheet on the screen. Game scores are totaled and compared to the series. If out of balance, the system will prompt you to reenter. **NOTE** - When entering scores onthis screen, you must depress the enter key after each one. It is not necessary to separate the scores with commas.
At the end of each team, you are allowed to enter teamhandicap (per game), as well as points won. The system requiresverrification (enter "y" or "n") before you may proceed.
In addition to updating the master files, the SCORES programalso creates the HISCORES.DET file for later processing by RECAP.
.EJECT
2. RECAP - This program sorts the results and prints theweekly standings sheet. The first line contains the Name of thebowling establishment; this field has not been parameterized andyou must make the appropriate change in the source program at line number 340. System date (DATE$) is used on this line also, so you should set the appropriate date in DOS prior to running thisprogram.
Prior to printing high individual and team scores, the system will prompt for the number of lines desired. You may print asmany or as few as your league wants - 3 or 4 is a suggested valuehere. Up to eight special message lines may be entered for League News or other special items.
The last processing step prompts for the next bowling date (MM,DD) and uses this to search the SCHEDULE.DET file to locate therecords for the next three bowling dates, which are then printedon the standings sheet. A sample output is attached.
C - Reporting Programs
1. RECORDD - This program permits display of team and bowler detail record sheets. Individual sheets can by printed with thePrtSc key.
2. RECORDP - Prints all team and bowler record sheets. Itis primarily intended to prepare the end of season hard copy forfiling.
3. SORTFILE - Prints the alphabetic "Book Average" listing for submission to ABC/WIBC each April.
4. FINAL - Prints the Final Standings sheet.
D - Special Utility Programs
The following programs were written to aid during theprogram development/testing phase. The user may find them usefulduring system modification.
1. PRINT - File dump of TEAMS.HDR and BOWLERS.HDR files.
2. DETAIL - File dump of TEAM.DET and BOWLER.DET files.
.eject
SETUP AND OPERATIONS
1. Program diskette. The system is supplied with an AUTOEXEC.BAT file which loads BASICA and runs the MENU program. In theauthor's system, he has included DOS, BASICA and several DOSutilities (e.g. DISKCOPY, CHKDSK) on the program diskette. Thisenables the system to be IPL'd and loaded automatically. Your own conventions may call for a different method, but be sure to invoke BASICA with the following command to accommodate the size andnumber of files:
BASICA MENU/F:5/S:512
2. Files Diskette. It is recommended that you dedicate aseparate diskette for files only. The programs are all written to run on the A disk and access all files on B, although thesereferences may be easily modified. If you have a very smallleague or have the 320kb dirves, you can probably get away withcombining programs and files on one floppy.
3. Initialization of system. To setup the league, you must runthe CREATE and SCHEDULE programs. They are independant of eachother so sequence of execution is of no concern. The CHANGEprogram can be run as desired to correct errors, add new bowlers,or shuffle bowlers around within the league.
4. Weekly Processing. Only two programs (SCORES followed byRECAP) need to be run each week. Remember to set the system dateto whatever value you want to have printed at the top of thesummary sheet. It is suggested that you print one master copy,from which xerographic copies can be made for distribution toleague members.
5. Backup. Backup of the files diskette on a regular basis ishighly recommemded. Remember that some fields cannot be accessedby the CHANGE program and the only way of recovering from fileerrors with the supplied code is to recreate the files and postall the weekly results again. However - if you do not need thesystem maintained detail records for teams and bowlers, it ispossible to use the CHANGE program to update total pins, games,etc. and recover from a lost file more easily. The detail filesare used only to print/display the individual record sheets.
BASICA MENU/F:display the individual record sheets.
